Dynamic load balancing in multiple video processing unit (VPU) systems

ABSTRACT

Systems and methods are provided for processing data. The systems and methods include multiple processors that each couple to receive commands and data, where the commands and/or data correspond to frames of video that include multiple pixels. An interlink module is coupled to receive processed data corresponding to the frames from each of the processors. The interlink module divides a first frame into multiple frame portions by dividing pixels of the first frame using at least one balance point. The interlink module dynamically determines a position for the balance point that minimizes differences between the workload of the processors during processing of commands and/or data of one or more subsequent frames.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.12/634,585 filed Dec. 9, 2009, which is a continuation of U.S. patentapplication Ser. No. 11/139,893, filed May 27, 2005, which issued asU.S. Pat. No. 7,649,537 on Jan. 19, 2010, which are hereby incorporatedby reference in their entirety.

This application is related to the following United States patentapplications:

Antialiasing System and Method, U.S. application Ser. No. 11/140,156,filed on May 27, 2005, which issued as U.S. Pat. No. 8,212,838, inventedby Arcot J. Preetham, Andrew S. Pomianowski, and Raja Koduri;

Multiple Video Processing Unit (VPU) Memory Mapping, U.S. applicationSer. No. 11/139,917, filed on May 27, 2005, which issued as U.S. Pat.No. 7,663,635, invented by Philip J. Rogers, Jeffrey Cheng, DmitrySemiannokov, and Raja Koduri;

Applying Non-Homogeneous Properties to Multiple Video Processing Units(VPUs), U.S. application Ser. No. 11/140,163, filed on May 27, 2005,which issued as U.S. Pat. No. 8,054,314, invented by Timothy M. Kelley,Jonathan L. Campbell, and David A. Gotwalt;

Frame Synchronization in Multiple Video Processing Unit (VPU) Systems,U.S. application Ser. No. 11/140,114, filed on May 27, 2005, invented byRaja Koduri, Timothy M. Kelley, and Dominik Behr;

Synchronizing Multiple Cards in Multiple Video Processing Unit (VPU)Systems, U.S. application Ser. No. 11/139,744, filed on May 27, 2005,invented by Syed Athar Hussain, James Hunkins, and Jacques Vallieres;

Compositing in Multiple Video Processing Unit (VPU) Systems, U.S.application Ser. No. 11/140,165, filed on May 27, 2005, which issued asU.S. Pat. No. 7,613,346, invented by James Hunkins and Raja Koduri; and

Computing Device with Flexibly Configurable Expansion Slots, and Methodof Operation, U.S. application Ser. No. 11/140,040, filed on May 27,2005, which issued as U.S. Pat. No. 7,539,801, invented by Yaoqiang(George) Xie and Roumen Saltchev.

Each of the foregoing applications is incorporated herein by referencein its entirety.

TECHNICAL FIELD

The invention is in the field of graphics and video processing.

BACKGROUND

Graphics and video processing hardware and software continue to becomemore capable, as well as more accessible, each year. Graphics and videoprocessing circuitry is typically present on an add-on card in acomputer system, but is also found on the motherboard itself. Thegraphics processor is responsible for creating the picture displayed bythe monitor. In early text-based personal computers (PCs) this was arelatively simple task. However, the complexity of moderngraphics-capable operating systems has dramatically increased the amountof information to be displayed. In fact, it is now impractical for thegraphics processing to be handled by the main processor, or centralprocessing unit (CPU) of a system. As a result, the display activity hastypically been handed off to increasingly intelligent graphics cardswhich include specialized coprocessors referred to as graphicsprocessing units (GPUs) or video processing units (VPUs).

In theory, very high quality complex video can be produced by computersystems with known methods. However, as in most computer systems,quality, speed and complexity are limited by cost. For example, costincreases when memory requirements and computational complexityincrease. Some systems are created with much higher than normal costlimits, such as display systems for military flight simulators. Thesesystems are often entire one-of-a-kind computer systems produced in verylow numbers. However, producing high quality, complex video atacceptable speeds can quickly become prohibitively expensive for even“high-end” consumer-level systems. It is therefore an ongoing challengeto create VPUs and VPU systems that are affordable for mass production,but have ever-improved overall quality and capability.

Another challenge is to create VPUs and VPU systems that can deliveraffordable, higher quality video, do not require excessive memory,operate at expected speeds, and are seamlessly compatible with existingcomputer systems.

INCORPORATION BY REFERENCE

All publications and patent applications mentioned in this specificationare herein incorporated by reference to the same extent as if eachindividual publication or patent application was specifically andindividually indicated to be incorporated by reference.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of a video processing system according to anembodiment.

FIG. 2 is a more detailed block diagram of a video processing systemaccording to an embodiment.

FIG. 3 is a block diagram of various components of a video processingsystem according to an embodiment.

FIG. 4 is a more detailed block diagram of a video processing system,which is a configuration similar to that of FIG. 3 according to anembodiment.

FIG. 5 is a diagram of a one-card video processing system according toan embodiment.

FIG. 6 is a diagram of a one-card video processing system according toan embodiment.

FIG. 7 is a diagram of a two-card video processing system according toan embodiment.

FIG. 8 is a diagram of a two-card video processing system according toan embodiment.

FIG. 9 is a block diagram of an interlink module (IM) according to anembodiment.

FIG. 10 is a diagram illustrating various load balancing modes accordingto an embodiment.

FIG. 11 is a flow diagram of dynamic load balancing (DLB), under anembodiment.

FIG. 12A is an example rendering of a triangle using DLB with ahorizontal balance point, under an embodiment.

FIG. 12B is an example rendering of a triangle using DLB with a verticalbalance point, under an embodiment.

FIG. 13 is a block diagram of path control logic of an interlink module(IM) according to an embodiment.

FIG. 14 is a block diagram of I2C paths according to a dongleembodiment.

FIG. 15 is a block diagram of I2C paths of an interlink module (IM)according to an embodiment.

FIG. 16 is a block diagram of I2C paths on a VPU card according to anembodiment.

DETAILED DESCRIPTION

An improved system and method for video processing is described herein.Embodiments include a video processing system with at least one graphicsprocessing unit (GPU) or video processing unit (VPU). As used herein,GPU and VPU are interchangeable terms. In various embodiments, renderingtasks are shared among the VPUs in parallel to provide improvedperformance and capability with minimal increased cost. Respective VPUsin the system cooperate to produce a frame to be displayed. In variousembodiments, data output by different VPUs in the system is combined, ormerged, or composited to produce a frame to be displayed. In oneembodiment, the system is programmable such that various modes ofoperation are selectable, including various compositing modes, andvarious modes of task sharing or load balancing between multiple VPUs.

FIG. 1 is a block diagram of a video processing system 100 according toan embodiment. The system 100 includes an application 102. Theapplication 102 is an end user application that requires videoprocessing capability, such as a video game application. The application102 communicates with application programming interface (API) 104.Several APIs are available for use in the video processing context. APIswere developed as intermediaries between the application software, suchas the application 102, and video hardware on which the applicationruns. With new chipsets and even entirely new hardware technologiesappearing at an increasing rate, it is difficult for applicationsdevelopers to take into account, and take advantage of, the latesthardware features. It is also becoming impossible to write applicationsspecifically for each foreseeable set of hardware. APIs preventapplications from having to be too hardware specific. The applicationcan output graphics data and commands to the API in a standardizedformat, rather than directly to the hardware. Examples of available APIsinclude DirectX (from Microsoft) and OpenGL (from Silicon Graphics).

The API 104 can be any one of the available APIs for running videoapplications. The API 104 communicates with a driver 106. The driver 106is typically written by the manufacturer of the video hardware, andtranslates the standard code received from the API into a native formatunderstood by the hardware. The driver allows input from, for example,an application, process, or user to direct settings. Such settingsinclude settings for selecting modes of operation, including modes ofoperation for each of multiple VPUs, and modes of compositing frame datafrom each of multiple VPUs, as described herein. For example, a user canselect settings via a user interface (UI), including a UI supplied tothe user with video processing hardware and software as describedherein.

In one embodiment, the video hardware includes two video processingunits, VPU A 108 and VPU B 110. In other embodiments there can be lessthan two or more than two VPUs. In various embodiments, VPU A 108 andVPU B 110 are identical. In various other embodiments, VPU A 108 and VPUB 110 are not identical. The various embodiments, which includedifferent configurations of a video processing system, will be describedin greater detail below.

The driver 106 issues commands to VPU A 108 and VPU B 110. The commandsissued to VPU A 108 and VPU B 110 at the same time are for processingthe same frame to be displayed. VPU A 108 and VPU B 110 each execute aseries of commands for processing the frame. The driver 106 programmablyinstructs VPU A 108 and VPU B 110 to render frame data according to avariety of modes. For example, the driver 106 programmably instructs VPUA 108 and VPU B 110 to render a particular portion of the frame data.Alternatively, the driver 106 programmably instructs each of VPU A 108and VPU B 110 to render the same portion of the frame data.

When either or both of VPU A 108 and VPU B 110 finishes executing thecommands for the frame, the frame data is sent to a compositor 114. Thecompositor 114 is optionally included in an interlink module 112, asdescribed more fully below. VPU A 108 and VPU B 110 cooperate to producea frame to be displayed. In various embodiments, the frame data fromeach of VPU A 108 and VPU B 110 is combined, or merged, or composited inthe compositor 114 to generate a frame to be rendered to a display 130.As used herein, the terms combine, merge, composite, mix, or interlinkall refer to the same capabilities of the IM 112 and/or compositor 114as described herein.

FIG. 2 is a block diagram of a system 200 according to an embodiment.The system 200 includes components or elements that may reside onvarious components of a video-capable computer system. In one embodimentan application 202, a driver 204, and a shared memory 205 reside on ahost computer system, while remaining components reside onvideo-specific components, including one or more video cards, but theinvention is not so limited. Any of the components shown could resideanywhere or, alternatively, various components could access othercomponents remotely via a wired or wireless network. The application 202is an end user application that requires video processing capability,such as a video game application. The application 202 communicates withapplication programming interface (APT) 204. The APT 204 can be any oneof the available graphics, or video, or 3D APIs including DirectX (fromMicrosoft) and OpenGL (from Silicon Graphics).

The API 204 communicates with a driver 206. The driver 206 is writtenspecifically for the system 200, and translates the standard codereceived from the API 204 into a native format understood by the VPUcomponents, which will be explained more fully below.

In one embodiment, the system 200 further includes two VPUs, VPU A 208and VPU B 210. The invention is not limited to two VPUs. Aspects of theinvention as described herein would be workable with one VPU withmodifications available to one of ordinary skill in the art. However, inmost instances the system would be less efficient with one VPU than withmore than one VPU. Various embodiments also include more than two VPUs.Systems with more than two are workable with modifications available toone of ordinary skill in the art, and in most instances would providebetter efficiency than a system with two VPUs. In various embodimentsVPU A 208 and VPU B 210 can be on one or more video cards that eachincludes a video processor and other associated hardware. As will beexplained further below, the invention is not so limited. For example,more than one VPU can be resident on one card or board. However, asreferred to herein a VPU is intended to include at least a videoprocessor.

VPU A 208 and VPU B 210 receive commands and data from the driver 206through respective ring buffers A 222, and B 224. The commands instructVPU A 208 and VPU B 210 to perform a variety of operations on the datain order to ultimately produce a rendered frame for a display 230.

The driver 206 has access to a shared memory 205. In one embodiment, theshared memory 205, or system memory 205, is memory on a computer systemthat is accessible to other components on the computer system bus, butthe invention is not so limited.

In one embodiment, the shared memory 205, VPU A 208 and VPU B 210 allhave access to a shared communication bus 234, and therefore to othercomponents on the bus 234. In one embodiment, the shared communicationbus 234 is a peripheral component interface express (PCIE) bus, but theinvention is not so limited.

The PCIE bus is specifically described in the following documents, whichare incorporated by reference herein in their entirety:

PCI Express™, Base Specification, Revision 1.1, Mar. 28, 2005;

PCI Express™, Card Electromechanical Specification, Revision 1.1, Mar.28, 2005;

PCI Express™, Base Specification, Revision 1.a, Apr. 15, 2003; and

PCI Express™, Card Electromechanical Specification, Revision 1.0a, Apr.15, 2003.

The Copyright for all of the foregoing documents is owned by PCI-SIG.

In one embodiment, VPU A 208 and VPU B 210 communicate directly witheach other using a peer-to-peer protocol over the bus 234, but theinvention is not so limited. In other embodiments, there may be a directdedicated communication mechanism between VPU A 208 and VPU B 210. Inyet other embodiments, local video memory 226 and 227 may be shared,which may eliminate the need for some of the communications between VPUA 208 and VPU B 210.

VPU A 208 and VPU B 210 each have a local video memory 226 and 228,respectively, available. In various embodiments, one of the VPUsfunctions as a master VPU and the other VPU functions as a slave VPU,but the invention is not so limited. In other embodiments, the multipleVPUs could be peers under central control of another component. In oneembodiment, VPU A 208 acts as a master VPU and VPU B 210 acts as a slaveVPU.

In one such embodiment, various coordinating and combining functions areperformed by an interlink module (IM) 212 that is resident on a samecard as VPU A 208. This is shown as IM 212 enclosed with a solid line.In such an embodiment, VPU A 208 and VPU B 210 communicate with eachother via the bus 234 for transferring inter-VPU communications (e.g.,command and control) and data. For example, when VPU B 210 transfers anoutput frame to IM 212 on VPU A 208 for compositing (as shown in FIG. 1for example), the frame is transferred via the bus 234.

In various other embodiments, the IM 212 is not resident on a VPU card,but is an independent component with which both VPU A 208 and VPU B 210communicate. One such embodiment includes the IM 212 in a “dongle” thatis easily connected to VPU A 208 and VPU B 210. This is indicated in thefigure by the IM 212 enclosed by the dashed line. In such an embodiment,VPU A 208 and VPU B 210 perform at least some communication through anIM connection 232. For example, VPU A 208 and VPU B 210 can communicatecommand and control information using the bus 234 and data, such asframe data, via the IM connection 232.

There are many configurations of the system 200 contemplated asdifferent embodiments of the invention. FIGS. 13-17 as described belowillustrate just some of these embodiments.

FIG. 3 is a block diagram of various components of a system 300according to an embodiment. The system 300 includes a master VPU card352 and a slave VPU card 354. The master VPU card 352 includes a masterVPU 308, and the slave VPU card 354 includes a slave VPU B 310. In oneembodiment, VPUs 308 and 310 each communicate via a PICE bus 334. In oneembodiment, the PCIE bus 334 is a X16 bus that is split into two X8 PCIEbuses 335. In one embodiment, VPU A 308 and VPU B 310 communicate onlythrough the bus 335. In alternative embodiments, VPU A 308 and VPU B 310communicate partially through bus 335 and partially through dedicatedintercard connection 337. In yet other embodiments, VPU A 308 and VPU B310 communicate exclusively through the connection 337.

The master VPU card 352 includes an IM 312. In an embodiment in whichVPU A 308 and VPU B 310 communicate via the bus 335, each VPU processesframe data as instructed by the driver. As an example in FIG. 3, thesystem 300 is performing video processing in a “scissoring” loadbalancing mode as described below. Master VPU A 308 generates an output309 and slave VPU B 310 generates an output 311. The outputs 309 and 311are input to the IM 312 for compositing, as described further below. Inone embodiment, the slave VPU B 310 transfers its output 311 to the IM312 via the buses 335 and 334 as shown by the dotted path 363. In oneembodiment, the slave VPU B 310 transfers its output 311 to the IM 312via the dedicated intercard connection 337 as shown by the dotted path361. The IM 312 combines the outputs 309 and 111 to produce a frame fordisplay. This frame is output to a display 330 by the IM 312 via aconnector 341.

The master VPU card 352 includes connectors 340 and 341. The slave VPUcard 354 includes connectors 342 and 343. Connectors 340, 341, 342 and343 are connectors appropriate for the purpose of transmitting therequired signals as known in the art. For example, the connector 341 isa digital video in (DVI) connector in one embodiment. There could bemore or less than the number of connectors shown in the system 300.

In one embodiment, the various configurations described herein areconfigurable by a user to employ any number of available VPUs for videoprocessing. For example, the system 300 includes two VPUs, but the usercould choose to use only one VPU in a pass-through mode. In such aconfiguration, one of the VPUs would be active and one would not. Insuch a configuration, the task sharing or load balancing as describedherein would not be available. However, the enabled VPU could performconventional video processing. The dotted path 365 from VPU card B 354to the display 330 indicates that slave VPU B 310 can be used alone forvideo processing in a pass-through mode. Similarly, the master VPU A 308can be used alone for video processing in a pass-through mode.

FIG. 4 is a more detailed block diagram of a system 400, which is aconfiguration similar to that of FIG. 3 according to an embodiment. Thesystem 400 includes two VPU cards, a master VPU card 452 and a slave VPUcard 454. The master VPU card 452 includes a master VPU A 408, and theslave VPU card 454 includes a slave VPU B 410.

The master VPU card 452 also includes a receiver 448 and a transmitter450 for receiving and transmitting, in one embodiment, TDMS signals. Adual connector 445 is a DMS connector in an embodiment. The master cardfurther includes a DVI connector 446 for outputting digital videosignals, including frame data, to a display. The master VPU card 452further includes a video digital to analog converter (DAC). An interlinkmodule (IM) 412 is connected between the VPU A 408 and the receivers andtransmitters as shown. The VPU A 408 includes an integrated transceiver(labeled “integrated”) and a digital video out (DVO) connector.

The slave VPU card 454 includes two DVI connectors 447 and 448. Theslave VPU B 410 includes a DVO connector and an integrated transceiver.As an alternative embodiment to communication over a PCIE bus (notshown), the master VPU card 452 and the slave VPU card 454 communicatevia a dedicated intercard connection 437.

FIGS. 5-7 are diagrams of further embodiments of system configurations.FIG. 5 is a diagram of a one-card system 500 according to an embodiment.The system 500 includes a “supercard” or “monstercard” 556 that includesmore than one VPU. In one embodiment, the supercard 556 includes twoVPUs, a master VPU A 508 and a slave VPU B 510. The supercard 556further includes an IM 512 that includes a compositor for combining orcompositing data from both VPUs as further described below. It is alsopossible, in other embodiments, to have a dedicated on-card inter-VPUconnection for inter-VPU communication (not shown). In one embodiment,the master VPU A 508 and the slave VPU B 510 are each connected to an X8PCIE bus 535 which comes from a X16 PCIE bus 534.

The system 500 includes all of the multiple VPU (also referred to asmultiVPU) functionality described herein. For example, the master VPU A508 processes frame data as instructed by the driver, and outputsprocessed frame data 509 to the IM 512. The slave VPU B 510 processesframe data as instructed by the driver, and outputs processed frame data511, which is transferred to the IM 512 for combining or compositing.The transfer is performed via the PCIE bus 534 or via a dedicatedinter-VPU connection (not shown), as previously described with referenceto system 300. In either case, the composited frame is output from theIM 512 to a display 530.

It is also possible to disable the multiVPU capabilities and use one ofthe VPUs in a pass-through mode to perform video processing alone. Thisis shown for example by the dashed path 565 which illustrates the slaveVPU B 510 connected to a display 530 to output frame data for display.The master VPU A 508 can also operate alone in pass-through mode byoutputting frame data on path 566.

FIG. 6 is a diagram of a one-card system 600 according to an embodiment.The system 600 includes a “supercard” or “monstercard” 658 that includesmore than one VPU. In one embodiment, the supercard 658 includes twoVPUs, a master VPU A 608 and a slave VPU B 610. The supercard 658further includes an IM 612 that includes a compositor for combining orcompositing data from both VPUs as described herein. It is alsopossible, in other embodiments, to have a dedicated on-card inter-VPUconnection for inter-VPU communication (not shown). In one embodiment,the master VPU A 608 and the slave VPU B 610 are each connected to a X16PCIE bus 634 through an on-card bridge 681.

The system 600 includes all of the multiVPU functionality describedherein. For example, the master VPU A 608 processes frame data asinstructed by the driver, and outputs processed frame data 609 to the IM612. The slave VPU B 610 processes frame data as instructed by thedriver, and outputs processed frame data 611, which is transferred tothe IM 612 for combining or compositing. The transfer is performed viathe PCIE bus 634 or via a dedicated inter-VPU connection (not shown), aspreviously described with reference to system 300. In either case, thecomposited frame is output from the IM 612 to a display (not shown).

It is also possible to disable the multiVPU capabilities and use one ofthe VPUs in a pass-through mode to perform video processing alone. Thisis shown for example by the dashed path 665 which illustrates the slaveVPU B 610 connected to an output for transferring a frame for display.The master VPU A 608 can also operate alone in pass-through mode byoutputting frame data on path 666.

FIG. 7 is a diagram of a two-card system 700 according to an embodiment.The system 700 includes two peer VPU cards 760 and 762. VPU card 760includes a VPU A 708, and VPU card 762 includes a VPU 710. In oneembodiment, VPU A 708 and VPU 710 are identical. In other embodimentsVPU A 708 and VPU B 710 are not identical. VPU A 708 and VPU 710 areeach connected to an X8 PCIE bus 735 that is split from a X16 PCIE bus734. VPU A 708 and VPU 710 are further each connected to output datathrough a card connector to an interlink module (IM) 712. In oneembodiment, the IM 712 is an integrated circuit in a “dongle” that iseasily connectable to VPU card 760 and VPU card 762. In one embodiment,the IM 712 is an integrated circuit specifically designed to include allof the compositing functionality described herein. The IM 712 merges orcomposites the frame data output by VPU A 708 and VPU 710 and outputs adisplayable composited frame to a display 730.

FIG. 8 is a diagram of a two-card system 800 according to an embodiment.The system 800 is similar to the system 700, but is configured tooperate in a by-pass mode. The system 800 includes two peer VPU cards860 and 862. VPU card 860 includes a VPU A 808, and VPU card 862includes a VPU B 810. In one embodiment, VPU A 808 and VPU B 810 areidentical. In other embodiments VPU A 808 and VPU B 810 are notidentical. VPU A 808 and VPU B 810 are each connected to an X8 PCIE bus835 that is split from a X16 PCIE bus 834. VPU A 808 and VPU B 810 arefurther each connected through a card connector to output data to aninterlink module (IM) 812. In one embodiment, the IM 812 is anintegrated circuit in a “dongle” that is easily connectable to VPU card860 and VPU card 862. In one embodiment, the IM 812 is an integratedcircuit specifically designed to include all of the compositingfunctionality described herein. The IM 812 is further configurable tooperate in a pass-through mode in which one of the VPUs operates aloneand the other VPU is not enabled. In such a configuration, thecompositing as described herein would not be available. However, theenabled VPU could perform conventional video processing. In system 800,VPU A 808 is enabled and VPU B 810 is disabled, but either VPU canoperate in by-pass mode to output to a display 830.

The configurations as shown herein, for example in FIGS. 3-8, areintended as non-limiting examples of possible embodiments. Otherconfigurations are within the scope of the invention as defined by theclaims. For example, other embodiments include a first VPU installed onor incorporated in a computing device, such as a personal computer (PC),a notebook computer, a personal digital assistant (PDA), a TV, a gameconsole, a handheld device, etc. The first VPU can be an integrated VPU(also known as an integrated graphics processor, or IGP), or anon-integrated VPU. A second VPU is installed in or incorporated in adocking station or external enclosed unit. The second VPU can be anintegrated VPU or a non-integrated VPU.

In one embodiment, the docking station is dedicated to supporting thesecond VPU. The second VPU and the first VPU communicate as describedherein to cooperatively perform video processing and produce an outputas described. However, in such an embodiment, the second VPU and thefirst VPU communicate via a cable or cables, or another mechanism thatis easy to attach and detach. Such an embodiment is especially usefulfor allowing computing devices which may be physically small and havelimited video processing capability to significantly enhance thatcapability through cooperating with another VPU.

It will be appreciated by those of ordinary skill in the art thatfurther alternative embodiments could include multiple VPUs on a singledie (e.g., two VPUs on a single die) or multiple cores on a singlesilicon chip.

FIG. 9 is a block diagram of an interlink module (IM) 912 according toan embodiment. All rendering commands are fetched by each VPU in thesystem. In any one of the multiVPU configurations described herein,after the VPUs execute the fetched commands, the IM 912 merges thestreams of pixels and control lines from the multiple VPUs and outputs asingle digital video output (DVO) stream.

The IM 912 includes a master input port that receives a DVO stream froma master VPU. The master VPU input can be from a TDMS receiver in a“dongle” configuration such as those shown in systems 700 and 800. Themaster VPU input can alternatively come from a master VPU on a masterVPU card in a multi-card configuration, as shown for example in systems300 and 400. A synchronization register 902 receives the DVO data fromthe master VPU.

The IM 912 further includes a slave input port that receives a DVOstream from a slave VPU. The slave VPU input can be from a TDMS receiverin a “dongle” configuration such as those shown in systems 700 and 800or a card configuration as in systems 300 and 400. The slave VPU inputcan alternatively come from a slave VPU on a “super” VPU cardconfiguration, as shown for example in systems 500 and 600. The IM 912includes FIFOs 904 on the slave port to help synchronize the inputstreams between the master VPU and the slave VPU.

The input data from both the master VPU and the slave VPU aretransferred to an extended modes mixer 914 and to a multiplexer (MUX)916. The IM 912 is configurable to operate in multiple compositingmodes, as described herein. When the parts of the frame processed byboth VPUs are combined, either by the extended modes mixer 914, or byselecting only non-black pixels for display, as further described below,the entire frame is ready to be displayed.

Control logic determines which compositing mode the IM 912 operates in.Depending on the compositing mode, either the extended modes mixer 914or the MUX 916 will output the final data. When the MUX 916 is used,control logic including a black register 906 and a MUX path logic andblack comparator 908, determines which master or slave pixel is passedthrough the MUX 916. Data is output to a TDMS transmitter 918 or a DAC920.

The black register is used to allow for control algorithms to set afinal black value that has been gamma adjusted.

In one embodiment, the inter-component communication among the VPUs andthe IM 912 includes I2C buses and protocols.

Operating modes, including compositing modes, are set through acombination of I2C register bits 924 and TMDS control bits 922 as shownin Table 1.

TABLE 1 Operational Modes and Control Bits Category Main Sub I2C BitsTMDS Cntr Bits Notes Passthru Slave INTERLINK_ENABLE = 0 n/a Uses 1^(st)I2C access to CONTROL_BITS_2: Bit 3 = x determine path Passthru MasterINTERLINK_ENABLE = 0 n/a Uses 1^(st) I2C access to CONTROL_BITS_2: Bit 3= x determine path Interlink AFR_MANUAL INTERLINK_ENABLE = 1 AFR_MAN_ON*= 0 xAFR_MAS state CONTROL_BITS_2: Bit 3 = 0 AFR_AUTO* = 1 changescontrols the next data path Interlink AFR_AUTO INTERLINK_ENABLE = 1AFR_MAN_ON* = 0 CONTROL_BITS_2: Bit 3 = 0 AFR_AUTO* = 0 InterlinkBLACKING INTERLINK_ENABLE = 1 AFR_MAN_ON* = 1 Uses black pixels toCONTROL_BITS_2: Bit 3 = 0 AFR_AUTO* = x determine data path InterlinkSuper AA INTERLINK_ENABLE = x n/a CONTROL_BITS_2: Bit CONTROL_BITS_2:Bit 3 = 1 4-7 determines extended mode

There are two separate data paths through the IM 912 according to anembodiment. The two input pixel streams from the respective VPUs areeither processed through the MUX 916 (in pass-through mode, or“standard” interlink modes), or through the mixer 914 in extended modes.In one embodiment, the extended modes include a super antialiasing mode,or “SuperAA mode”, as described in copending U.S. patent applicationSer. No. 11/140,156, titled “Antialiasing System and Method”, which ishereby incorporated by reference in its entirety.

In the MUX 916, just one pixel from either VPU A or VPU B is selected topass through, and no processing of pixels is involved. In the extendedmodes mixer 914, processing is done on a pixel by pixel basis. In theSuperAA mode, for example, the pixels are processed, averaged together,and reprocessed. In one embodiment, the processing steps involve usingone or more lookup tables to generate intermediate or final results.

The selection between the MUX 916 path and the mixer 914 path isdetermined by I2C register bits and control bits. For example, the mixer914 path is selected if:

-   -   ENABLE_INTERLINK=1 (I2C register)    -   and CONTROL_BITS_2: Bit 3 and Bit 4=1 (ExtendedModes and        SuperAA) (else MUX).

In one embodiment, the IM has three ports, two input ports and oneoutput port.

The output port configuration is split into two parts. The DAC is drivenacross a 24 bit single data rate (SDR) interface. The TMDS is drivenwith a double data rate (DDR) interface; a 12 pin interface for TMDSsingle link, and a 24 pin interface for TMDS dual link. The I2C controlbit registers determines this configuration.

There are three primary pixel clock domains. Both the master and slaveinputs come in on their own separate domains. The IM uses the DVO clockdomain for all internal paths and the final output. The DVO clock isgenerated by the active input port in pass-through mode and from themaster input clock in interlink mode.

The master input bus (data and control) goes through a synchronizer asit passes into the DVO clock domain, imparting a 2-4 clock delay. Theslave input bus (data and control) goes into a FIFO which issynchronized on its output to the DVO clock domain. The outputs of bothpaths are routed to a MUX or extended modes mixer which then outputs asingle bus width data output.

In slave pass-through mode the slave FIFO is set into pass-through mode,while in interlink mode, it is used as a standard FIFO. For slavepass-through mode, the control bits go through the FIFO with the pixeldata. In interlink mode, sAFR_MAS goes through with the data, and thecontrol bits are ignored from the slave input port.

I/Os that use DDR clocking are split into double wide buses (e.g.,12-bit DDR input becomes 24 bits internally). This is to avoid having torun the full clock speed through the IM.

In one embodiment, there is one FIFO on the IM, located on the slavechannel. Twenty-four (24) bits of pixel data flow through the FIFO insingle TMDS mode, and 48 bits of data flow through the FIFO in dual TMDSmode. The slave port's control bits are also carried through this FIFOwhen in pass-through mode, slave path. When in interlink mode, thecontrol bits are ignored, and instead of the control bits the sAFR_MASbit is carried through in parallel with the pixel data.

When in single link TMDS mode (CONTROL_BITS: Dual_Link_Mode bit=0), theextra 24 bits of data for dual link are not clocked to conserve power.

On power up the FIFOs should be set to empty. FIFOs are also clearedwhen the ENABLE_INTERLINK bit toggles to 1 or if theCONTROL_ONESHOTS:FIFO_Clear bit is set to 1.

The slave FIFO has two watermarks (registers FIFO_FILL, FIFO_STOP). TheIM drives the SlavePixelHold pin depending on how full the FIFO is andthe values in these registers. If the slave FIFO has FIFO_FILL or fewerentries in use, the SlavePixelHold should go low. If the slave FIFO hasFIFO_STOP or more entries in use, the SlavePixelHold should go high.

“Load balancing” refers to how work is divided by a driver forprocessing by multiple system VPUs. In various embodiments, theprocessed data output by each VPU is composited according to one ofmultiple compositing modes of the IM 12, also referred to herein as“interlinking modes” and “compositing modes”. The IM 12 supportsnumerous methods for load balancing between numerous VPUs, includingsuper-tiling, scissoring and alternate frame rendering (“AFR”), all ofwhich are components of “Blacking”. These modes are described below.FIG. 10 is a diagram illustrating various load balancing modes performedby the system as described. Frame data from various VPUs in the systemis processed according to a load balancing mode and composited in acompositor 114, as described herein, to generate a displayable frame.Alternative embodiments of the IM may use any of the compositing modesin any combination across any number of VPUs.

For Super-Tiling, software driver control determines the tile size andalternates between image data and black tiles so that, between themaster and slave VPUs, each frame is fully painted. The IM 112 passesthrough the non-black pixels (image data) creating a super tiling-typesplit between the master and slave inputs. The tile sizes can bedynamically adjusted every pair of master and slave frames if desired.Super-Tiling may divide a display screen into a chess board pattern forwhich each square/tile is 32×32, pixels for example. The image tiles arerendered on a first VPU of a multi-VPU system while the black tiles arerendered on a second VPU. Super-Tiling provides fine grain load sharingfor pixel processing within a frame of rendering, a more evendistribution of pixel load relative to other load balancing methods, andless complex driver implementation.

Scissoring divides a display screen into two parts, and this divisioncan be horizontal or vertical. While a horizontal split may be moreconvenient when considering software implementation and data transferflexibility, a vertical split may provide better load balancing. In thecontext of multiple VPUs, scissoring provides optimization opportunitiesin the direction of parallelizing data transfers with 3D rendering.Scissoring also supports methods in which the slave VPU (which performsthe majority of data transfers) does less work than the master VPU,thereby facilitating dynamic load balancing schemes between the masterand the slave VPUs.

Scissoring includes both Vertical Split Screen Blacking Control andHorizontal Split Screen Blacking Control. With Vertical Split ScreenBlacking Control, the drivers determine which side of a frame are outputfrom the master and slave VPU, so that between the two VPUs every frameis completely painted. The part of a frame that each VPU does not handleis cleared to black by the drivers. The IM 912 then interlinks the twoframes as a vertical split between the master and slave VPU. The splitdoes not have to be an even split of the screen (e.g., 50% rendered byeach VPU) and can be dynamically adjusted for every pair of master andslave frames.

Under Horizontal Split Screen Blacking Control, the software driversdetermine which upper or lower section of a frame are output from themaster and slave VPU. The drivers then clear to black the portions thatwill not hold valid frame buffer data and the IM 912 mixes the inputs asa horizontal split of the inputs. The split does not have to be an evensplit of the screen (e.g., 50% rendered by each VPU) and can bedynamically adjusted for every pair of master and slave frames.

Alternate Frame Rendering (“AFR”) performs load balancing at a framelevel. A “frame” as referred to herein includes a sequence of renderingcommands issued by the application before issuing a display bufferswap/flip command. AFR generally passes each new frame through to theoutput from alternating inputs of the IM 912. One VPU renders theeven-numbered frames and the other VPU renders the odd-numbered frames,but the embodiment is not so limited. The AFR allows performance scalingfor the entire 3D pipeline, and avoids render-to-texture card-to-carddata transfers for many cases.

The IM 912 of an embodiment may perform AFR under Manual Control, ManualControl with automatic VSync switching, or Blacking Control. When usingManual Control, the drivers manually select an input of the IM 912 for aframe after the next VSync. Using AFR using Manual Control with VSyncswitching, and following a next vertical blank, the IM 912 chooses theinput coupled to the master VPU as the output source and thenautomatically toggles between the master and slave VPU inputs on everyVSync. Using Blacking Control, the drivers alternate sending a fullypainted frame versus a cleared-to-black frame from the master and slaveVPUs; the IM 912 toggles between the master and slave frames as aresult.

As described above with reference to FIG. 9, the IM merges streams frommultiple VPUs to drive a display. The merging of streams uses Manual AFRcompositing and Blacking compositing (FIG. 10) but is not so limited.Both Manual AFR and Blacking compositing support AFR, which includesswitching the IM output alternately between two VPU inputs on aframe-by-frame basis. The Blacking with both horizontal screen split andvertical screen split includes a variable split offset controlled by theIM. The Blacking with Super-Tiling includes a variable tile sizecontrolled by the IM.

The control logic including the black register 906 and MUX path logicand black comparator 908 determines the compositing mode of the IM 912by controlling the MUX 916 to output a frame, line, and/or pixel from aparticular VPU. For example, when the TMDS control bits 922 select AFRManual compositing as described herein, the IM 912 alternately selectseach VPU to display alternating frames. As such, system drivers (notshown) determine the VPU source driven to the output. By setting thexAFR_MAS control bit 922 high, the MUX 916 of an embodiment couples themaster input port (master VPU output) to the IM output on the next frameto be displayed. In contrast, by setting the xAFR_MAS control bit 922low, the MUX 916 couples the slave input port (slave VPU output) to theoutput on the next frame to be displayed.

The AFR_AUTO bit of the TMDS control bits 922 enables automatic togglingthat causes the IM output to automatically switch or toggle between themaster and the slave inputs on every VSync signal. When the AFR_AUTO bitis asserted the IM begins rendering by coupling to the IM output theinput port selected by the xAFR_MAS bit. The IM automatically togglesits output between the master and slave inputs on every VSync signal,thereby ignoring the xAFR_MAS bit until the AFR_AUTO bit is de-asserted.The IM thus automatically controls the display of subsequent frames (orlines) alternately from each VPU.

The AFR Manual mode may also control a single VPU to drive the IM outputby setting the AFR_MAN_ON* bit to an asserted state. In contrast tocoupling the IM output alternately between two VPUs for each frame,AFR_MAN_ON* hit sets the IM output path according to the state of thexAFR_MAS bit and does not toggle the output between multiple VPUs forsubsequent frames or pixels.

The IM of an embodiment supports more advanced merging of streams frommultiple VPUs using Blacking compositing. The MUX path logic and blackcomparator 908, when operating under Blacking, controls the MUX 916 soas to provide the IM output from one of multiple VPUs on apixel-by-pixel basis. The decision on which pixels are to be displayedfrom each of a number of VPUs generally is a compare operation thatdetermines which VPU is outputting black pixels. This is a fairlyefficient and flexible method of intermixing that allows the drivers to“tune” the divisions, and the blacking can be done by clearing memory toblack once per mode set-up and then leaving it until the mode ischanged.

The Blacking generally receives a data stream from each of a first VPUand a second VPU, and compares a first pixel from the first VPU toinformation of a pixel color. The Blacking selects the first pixel fromthe first VPU when a color of the first pixel is different from thepixel color. However, Blacking selects a second pixel from the secondVPU when the color of the first pixel matches the pixel color. The firstpixel of the data stream from the first VPU and the second pixel of thedata stream from the second VPU occupy corresponding positions in theirrespective frames. The Blacking thus mixes the received digital videostreams to form a merged data stream that includes the selected one ofthe first and second pixels.

The drivers (e.g., referring to FIG. 1, driver 106 of video processingsystem 100) corresponding to the IM select Blacking compositing bydeactivating the AFR Manual mode at the IM. Deactivation of the Blackingmode is controlled by asserting the AFR_MAN_ON* bit of the TMDS controlbits 922. The drivers also set up the frame buffers by setting any pixelof a VPU to black when another one of multiple VPUs is to display thatpixel. This is similar in effect to a black chroma key affect but theembodiment is not so limited. If the pixels of all VPUs coupled to theIM are black the IM couples the pixel output from the master VPU to theIM output.

The IM uses the pixel clock and internal control lines to selectivelycouple an input port to the IM output on a pixel-by-pixel basis. In anexample system having two VPUs, the MUX path logic and black comparator908 performs compare-to-color operations so that output pixels from afirst VPU output are compared with the contents of the black register todetermine if the output pixels are a particular color. In an embodiment,the compare-to-color operations are compare-to-black operations, but the“black” color may be configurable to any pixel color. If the outputpixels are black then the MUX path logic and black comparator 908controls multiplexer 916 to output pixels (non-black) from the secondVPU. When the IM determines the output pixels from the first VPU are notblack then the MUX path logic and black comparator 908 controlsmultiplexer 916 to output the pixels from the first VPU.

Other compositing strategies are available and are not limited by the IM912. For example, extended interlink modes are also available that gobeyond the load sharing usage of the Manual AFR and Blacking modes.These modes, while not the standard interlinking used for pure speedgains by sharing the processing between multiple VPUs, enhance thesystem quality and/or speed by offloading functionality from the VPUs tothe IM 912. As one example of an extended mode, the IM 912 of anembodiment supports the “SuperAA” mode previously referred to inaddition to the Manual AFR and Blacking modes.

The multiple VPU systems described herein provide numerous mechanismsfor distributing the workload across the VPUs. These load balancingmethods include AFR, Scissoring, and Super-Tiling. The Scissoring modedivides the display into some number of portions or parts, where thescreen can be split horizontally or vertically using a “balance point”or “split point”. In a system having two VPUs, for example, the VPUscissor functionality controls the rendering during horizontal splittingso that one VPU renders only to the top portion and the other VPUrenders only to the bottom portion of the screen. Similarly, VPU scissorfunctionality controls the rendering during vertical splitting so thatone VPU renders only to the left portion and the other VPU renders onlyto the right portion of the screen.

Scissoring modes typically use static balance points that do not changeas applications run on the host system. These static balance points maylead to poor performance if the rendering load is not split evenlyacross the two portions of the screen. While a static balance point canbe chosen using application detection, this will not help applicationswhich vary the rendering load while running.

The multiple VPU system of an embodiment uses Dynamic Load Balancing(“DLB”) as an improvement to scissoring mode that allows the balancepoint to vary as applications are running to produce an optimal ornear-optimal split of the rendering load between the VPUs. The DLBdynamically determines an appropriate “balance point” or “split point”of the screen and moves or adjusts the balance point per frame so as toapproximately equalize the processing (e.g., pixel processing) workloadof rendering each portion of the display screen. An IM control algorithmcontrols the DLB of an embodiment without a direct connection betweenthe VPUs, thereby supporting multiple VPUs that each has no knowledge ofother VPUs that may be supporting the host system.

The multiple VPU system provides DLB without a direct connection betweenthe VPUs. Instead each VPU writes a specific identifier to a location inmemory at such time as the VPU completes rendering of a current frame.Upon completion of rendering operations for the current frame adetermination is made as to which of the multiple VPUs completedrendering operations last based on the identifier read from the memory.Thus, the VPU corresponding to the identifier in memory followingrendering of a current frame is the VPU that last finished renderingoperations for that frame.

In various embodiments, the identifier could be stored anywhere in thesystem accessible by all the VPUs in the system, including a systemmemory location.

Table 2 is an example sequence of commands submitted to the multiple VPUsystem during frame rendering, under an embodiment.

TABLE 2 VPU 0 VPU 1 1 Render VPU 0 portion of Render VPU 1 portion ofFrame N Frame N 2 Write 0x000000FF to system Write 0x0000FF00 to systemmemory location memory location 3 Synchronize with VPU 1 Synchronizewith VPU 0 4 Display Frame N Display Frame N

Rendering using DLB selects a compositing mode and initializes the DLBbased on information of a detected application running on the hostsystem. Initial instructions from the driver to each VPU specify via thecorresponding scissor register which region of the screen is to berendered by that VPU. The scissor register subsequently controls the VPUto only draw to the appropriate portion of the screen. The remainingregion of the screen is set to black at the end of the frame, but beforethe image is sent to the compositor.

The components of an embodiment may initialize the balance point viawriting of a variable to the scissor registers (corresponding to theVPUs) as in a static scissoring mode, but are not so limited. Thevariables written to the scissor registers, referred to as the “percenton master” variables, represent a percentage of a frame that is renderedby the VPU that corresponds to the scissor register holding the percenton master. The value of the percent on master variable is converted to anumber of scan lines to be rendered by the corresponding VPU. Thebalance point may be set for example so that the master VPU renders 50%of the display and the slave VPU renders the remaining 50% of thedisplay. In another example, the balance point may be set so that themaster VPU renders 55% of the display and the slave VPU renders theremaining 45% of the display.

Components of the multiple VPU system (e.g., system driver) dynamicallyinitialize or adjust the balance point for rendering a frame based oninformation of the rendering of one or more earlier frames. In so doingthe driver for example reads a pre-specified location (e.g., register)in system memory to which the VPUs write their respective identifiers inorder to determine the last VPU to finish rendering a particular frame.The VPU to last finish rendering will have its processing load reducedon subsequent frames (the next frame the control algorithm generates) asa result of the driver moving the balance point to reduce the portion ofthe rectangle rendered by the last-finishing VPU. The adjustment ofprocessing load is accomplished by providing different scissorrectangles to each different VPU so that each VPU renders a differentportion of the screen. The DLB thus allows for adjustment of how much isrendered with each VPU by adjusting the scissor registers on a per-framebasis.

In an embodiment, the balance point is adjusted for a frame usinginformation of rendering operations from two (2) frames earlier in theprocessing chain. This allows the system driver and/or other componentsto work in parallel by having the driver generate rendering commands forframe “N+2” while frame “N” is being rendered.

In adjusting the balance point, components of the multiple VPU systemlook back two (2) frames earlier, which may include several commandbuffers. This number of frames allows the system to look backwards inthe frame processing chain without having to stop and wait for the VPUsto finish rendering the current frame. The DLB therefore allows thecontrol algorithm and VPU hardware to overlap in terms of framerendering, so the control algorithm is generating commands for one frame(frame N+1) in advance of the VPU (rendering frame N) rendering thecommands. In DLB, after the control algorithm generates frame (N+1) itlooks at the results from rendering of frame N to determine anyadjustment in balance point needed during rendering of frame (N+2).

Upon completion of frame N rendering operations the system memory isread to determine the last of the multiple VPUs to complete renderingoperations for frame N. The last VPU to complete rendering operationscorresponds to the identifier read from system memory as describedherein. The balance point is adjusted or changed for frame N+2 in orderto reduce the number of pixels or portion of the frame rendered by thelast VPU to finish rendering of frame N. The balance point of anembodiment is adjusted in increments of one percent (1%) of at least oneof the display height (horizontal balance point), display width(vertical balance point), number of lines, and number of pixels, howeveralternative embodiments may use any percentage of these parameters. Thisbalance point may then be rounded to a VPU family specific pixelboundary.

In embodiments where VPUs are not rendering to shared memory, if anevent occurs which requires the rendering from the VPUs to be mergedmid-frame (for example, glCopyTexSubImage or other render to textureoperation, copying the image of VPU A to VPU B, and copying the image ofVPU B to VPU A, resulting in both VPUs having the full image followingthe copy), the balance point of an embodiment is reset to the originalbalance point to which the system was initialized. When events occurrequiring the rendering from each VPU to be merged mid-frame, both VPUsneed to complete rendering of the image in order to continue processingthat frame (e.g., a scene that includes a mirror displaying some or allof a screen image). These events typically include rendering of a typeof effect that requires all rendered information of a frame. Thisresetting is performed because the mid-frame merging or copying of datafrom multiple VPUs is generally fastest when the balance point is set soas to reduce the processing expense of transferring data across the PCIEbus.

The driver of an embodiment may be configured to control the slave VPUto render a smaller portion of the screen in a multiple VPUconfiguration. Consequently, an embodiment renders the smaller portionof the data (e.g., based on pixel count) on the slave VPU in order toreduce the amount of data transferred across the PCIE bus at the end ofa frame. For example, when the balance point is moved so that the masterVPU is rendering a smaller portion of the display area than the slaveVPU, components of the multiple VPU system may swap the display regionsrendered by the master and slave VPUs. Therefore, when a position of thebalance point has the master VPU rendering 49% and the slave VPUrendering 51% of the display, the driver swaps the display portionsbetween the VPUs. Following the swap, the master VPU renders the 51% ofthe display rendered by the slave VPU in the previous frame, while theslave VPU now renders the 49% of the display previously rendered by themaster VPU.

FIG. 11 is a flow diagram of dynamic load balancing 1100, under anembodiment. The DLB 1100 divides 1102 a first frame into multiple frameportions by dividing pixels of the first frame using at least onebalance point. The DLB 1100 renders 1104 each of the multiple frameportions using each of the processors. The last processor of themultiple processors to complete rendering of a respective frame portionof the first frame is then determined 1106. Components of the systemdynamically determine and adjust 1108 the balance point to reduce anumber of pixels processed by the last processor. One or more subsequentframes are rendered 1110 using the dynamically adjusted balance point.

FIG. 12A is an example rendering of a triangle 1200 using DLB with ahorizontal balance point, under an embodiment. The triangle 1700includes top 1200A and bottom 1200B portions. The balance point 1202 forthis example is set so that the slave VPU renders 50% of the display(bottom portion) and the master VPU renders the remaining 50% of thedisplay (top portion). When drawing the triangle 1200, the triangleframes are provided to both VPUs. The master VPU will, as a result ofthe scissor register setting, render the top 50% of the lines or pixelsof the display while at the same time the slave VPU renders the bottom50% of the lines or pixels of the display.

In this first frame rendering, the slave VPU will be the last to finishprocessing the frame and writing its identifier to system memory becausethe slave VPU is processing more pixels (the area of the triangle bottomportion 1200B processed by the slave VPU is larger than the area of thetriangle top portion 1200A). As a result of finishing last, the DLBadjusts the balance point 1202 for a subsequent frame via the scissorregister settings as described above. The new balance point 1204 reducesthe number of lines rendered by the slave VPU by 1% (50%−1%=49%) whileincreasing the number of lines rendered by the master VPU by 1%(50%+1%=51%).

In the next frame rendering, the slave VPU will again be the last tofinish processing the frame and writing its identifier to system memorybecause the slave VPU is still processing more pixels. As a result offinishing last, the DLB adjusts the balance point 1204 for a subsequentframe via the scissor register settings as described above. The newbalance point 1206 reduces the number of lines rendered by the slave VPUby 1% (49%−1%=48%) while increasing the number of lines rendered by themaster VPU by 1% (51%+1%=52%). The DLB operations continue as describedabove.

FIG. 12B is an example rendering using DLB with a vertical balancepoint, under an embodiment. The triangle 1250 includes right 1250R andleft 1250L portions. The balance point 1252 for this example is set sothat the slave VPU renders 50% of the display (left portion) and themaster VPU renders the remaining 50% of the display (right portion). Themaster VPU renders the right 50% of the lines or pixels of the displaywhile at the same time the slave VPU renders the left 50% of the linesor pixels of the display.

In the first frame rendering, the slave VPU will be the last to finishprocessing the frame and writing its identifier to system memory becausethe slave VPU is processing more pixels (the area of the triangle leftportion 1250L processed by the slave VPU is larger than the area of thetriangle right portion 1250R). As a result of finishing last, the DLBadjusts the balance point 1252 for a subsequent frame via the scissorregister settings as described above. The new balance point 1254 reducesthe number of lines rendered by the slave VPU by 1% (50%−1%=49%) whileincreasing the number of lines rendered by the master VPU by 1%(50%+1%=51%).

In the next frame rendering, the slave VPU will again be the last tofinish processing the frame and writing its identifier to system memorybecause the slave VPU is still processing more pixels. As a result offinishing last, the DLB adjusts the balance point 1254 for a subsequentframe via the scissor register settings as described above. The newbalance point 1256 reduces the number of lines rendered by the slave VPUby 1% (49%−1%=48%) while increasing the number of lines rendered by themaster VPU by 1% (51%+1%=52%). The DLB operations continue as describedabove.

When DLB is used in systems having more than two VPUs, the drivercontinues to adjust the balance point based on information of the lastVPU to write its identifier to a location in system memory. The portionof the rendering taken from the last VPU to write in these embodimentsis evenly distributed among the other VPUs of the system, but is not solimited.

Referring again to FIG. 9, the IM 912 supports multiple input modes andsingle or dual link TMDS widths, depending on the input connectivity.The IM 912 also includes counters that monitor the phase differencesbetween the HSyncs and VSyncs of the two inputs. The counters mayinclude a pixel/frame counter to assist in matching the clocks on thetwo input streams.

With reference to Table 3, in one embodiment, the IM 912 has threecounters 910. Each counter increments the master pixel clock and usesone of the VSyncs for latching and clearing.

If a read of an I2C counter is occurring, the update to that register isheld off until after the read is completed. If a write of the registeris occurring, then the read is delayed until the write is completed.Read delays are only a few IM internal clocks and therefore aretransparent to software.

TABLE 3 IM Counters Counter Name Bits Clock DescriptionCLKS_PER_FRAME_CTR 22 Master Number of master clocks per 1 slave framePixel uses slave VSync to determine frame edges every slave VSynclatches the count to CLKS_PER_FRAME and resets this counterS2M_VSYNC_PHASE_CTR 11 Master Number of lines displayed between Pixelslave VSync and master VSync latched to S2M_VSYNC_PHASE every masterVSync resets the count to 0 every slave VSync S2M_HSYNC_PHASE_CTR 12Master Number of pixels displayed between Pixel slave HSync and masterHSync latched to S2M_HSYNC_PHASE every master HSync resets the count to0 every slave HSync

The IM 912 may be used in a number of configurations as described above.In one configuration, referred to herein as a “dongle”, the IM 912receives two separate TMDS outputs, one each from two separate VPUs, andbrings them onto the dongle through two TMDS receivers. The separatereceivers then output two DVO streams directly into the IM 912 of thedongle. The IM 912 mixes the two received inputs into a single outputstream. The output DVO signals from the IM 912 are then fed either to aTMDS transmitter or through a DAC, both of which drive out through astandard DVI-I connector on the dongle.

In another configuration, referred to herein as an “on-card”configuration, the IM 912 receives two streams of DVO signals directlyfrom two VPUs that reside on the same card as the IM 912. This on-cardconfiguration does not use TMDS transmitters or receivers between theVPUs and the IM 912, in contrast to the dongle configuration. The IM 912mixes the two received inputs into a single output stream. The outputDVO signals from the IM 912 are then fed either to a TMDS transmitter orthrough a DAC, both of which drive out through a standard DVI-Iconnector for example.

The input streams received at the IM 912 inputs are referred to hereinas the “master input” and the “slave input”, and are received from themaster and slave VPUs, respectively. The master and slave VPUs may be ontwo separate cards or on a single “super” card. Either VPU can functionas the master or slave VPU.

The master VPU is used as the primary clock to which the slave issynchronized (“synced”). The master clock is not adjusted or tuned otherthan the normal card initialization process. The slave VPU is adjustedto run slightly ahead of the master VPU to allow for synchronization andFIFO latencies. The slave VPU uses a larger FIFO in order to compensatefor variances between the pixel clock rates of the two VPUs, while themaster VPU path uses a shallow FIFO to synchronize the master inputclock domain to the internal DVO clock domain. Flow control between themaster and slave VPUs includes initial synchronization of the two VPUsand then ongoing adjustments to the slave VPU to match the master VPU.The flow control includes clock adjustments via a pixel hold off signalgenerated by the IM 912 or driver action in response to counters withinthe IM 912.

The IM 912 as described above supports numerous operational modes,including Pass-through Mode and various Interlink Modes, as illustratedin Table 1. These operational modes are set through a combination of I2Cregister bits and the TMDS Control Bits as described herein.

Pass-through Mode is a mode in which an input of the IM 912 is passeddirectly through to the output (monitor). The input port used is chosenat power-up by the initial toggling of an I2C clock. The path can bechanged again by switching an ENABLE_INTERLINK register from “1” back to“0” and then toggling the I2C clock of the desired port.

Interlink Modes include numerous modes in which the IM 912 couplesinputs received from the master and slave VPUs to an output in variouscombinations. Dual VPU Interlink Modes of an embodiment include but arenot limited to Dual AFR Interlink Mode and Dual Blacking Interlink Mode.

Dual VPU Interlink Modes are modes in which both VPUs are being usedthrough manual AFR control or through blacking modes. Both IM 912 portsare output continuously during operations in these modes.

Dual AFR Interlink Mode includes modes in which the source of the IM 912output is alternated between the two input ports. It can either be donemanually by the IM 912 drivers or automatically once started based onVSync. Control of the Dual AFR Interlink Mode includes use of thefollowing bits/states: AFR_MAN_ON*=low; AFR_AUTO*=high or low; AFR_MAS(used to control which card is outputting at the time or to set thefirst card for the Auto switch).

FIG. 13 shows path control logic of the IM, under an embodiment. TheoClk signal is the output pixel clock. It is generated in slave passthrudirectly from the sClk from the slave port. In interlink or masterpass-through modes, it is generated directly from the mClk from themaster port with the same timings. oClk:mDE is the master port's mDEsignal synchronized into the oClk time domain.

Dual Blacking Interlink Mode includes modes in which both VPUs output inparallel and the IM 912 forms an output by selecting pixels on apixel-by-pixel basis by transmitting black pixel values for any pixel ofany VPU that should not be output. Control of the Dual BlackingInterlink Mode includes use of the following bit/state:AFR_MAN_ON*=high.

AFR_MAN_ON* is sent across the master TMDS Control Bit bus on bit no 2.It is clocked in with mClk, one clock before the rising edge of mDEafter the rising edge of mVSync. The action in response to it takesplace before the first pixel of this mDE active period hits the MUX.Other than this specific time, there is no direct response toAFR_MAN_ON*.

When AFR_MAN_ON* is active (LOW) and ENABLE_INTERLINK is set to 1 andthe ExtendedModes bit is 0, then the path set by the pixel MUX iscontrolled by the xAFR_MAN bits as described below.

The I2C register reflects the result after the resulting action occurs.It does not directly reflect the clocked in bit.

AFR_AUTO* is sent across the slave TMDS Control Bit bus on bit no 2. Itis clocked in with sClk timings and then synced to mClk. It is latchesin the clock before mDE goes high after the rising edge of mVSync. Theaction in response to it then occurs before the first pixel associatedwith the active mDE hits the MUX and only if AFR_MAN_ON* is low on thesame latching point.

When AFR_AUTO* and AFR_MAN_ON* are active and ENABLE_INTERLINK is set to1 and extended interlink modes are not active, then the path set by thepixel MUX is initially set to the master path. The path is thenautomatically toggled on every rising edge of mDE after the rising edgeof mVSync until AFR_AUTO* is deasserted.

The I2C register reflects the result after the resulting action occurs.It does not directly reflect the clocked in bit.

The mAFR_MAS is set from the master port on mLCTL[1] and sAFR_MAS is setfrom the slave port on sLCTL[1]. These two bits control which path isset by the pixel MUX when in Interlink mode, manual AFR control.

The mAFR_MAS is clocked directly in with mCLK. The sAFR_MAS is clockedin with sCLK and then synced to mCLK. The bits are latched on the risingclock edge before the rising edge of mDE. Both latched bits then go intoa logic block which detects a bit changing state. Depending on an I2Cregister bit, either after the rising edge of a VSync or an HSync, if abit is detected as having its state changed, the logic sets the pixelMUX when in AFR_MANUAL Interlink mode to match the path of the toggledbit. The MUX will not change during AFR_MANUAL interlink mode at anyother time.

If both bits toggle in the same updating time frame, then the masterpath is set.

Unlike the other control bits, the I2C register reflects the individualsynchronized bits going into the MUX control logic block clocked in withMClk and not the bits after the sync state.

Regarding data and control paths in the IM 912 of an embodiment, theDual VPU Interlink Mode works in routing modes that includepass-through, dual/single input AFR Manual interlink, and dual inputBlacking Interlink. These routing modes describe which of the data andcontrol lines from the two receivers get transmitted out of the IM 912via the transmitter or DAC. Table 4 chows the data, control, and clockrouting by muting mode of the IM 912, under an embodiment.

The clock is the pixel clock, the internal control lines are the linesthat connect between the TMDS transmitter and receivers (and IM 912),and the external control lines are lines that are not processed by theTMDS circuitry such as I2C and Hot Plug. The Slave pixel hold off signalgoes directly between the IM 912 and the Slave DVI VSync pin.

TABLE 4 Routing Internal Bypass Mode Clock Control Control Data NotesPass- Master or Master or Master or Master or Set by first I2C clocktoggling Through Slave Slave Slave Slave AFR Master or Master or Masteror Master or Set by AFR_MAN control bit Manual Slave Slave Slave SlaveBlacking Master Master Master Master and Data is interlinked dependingSlave on black pixels

Pass-Through occurs when using the IM 912 in single-VPU Mode and beforethe drivers set up the IM 912 and VPUs for the dual-VPU mode. At powerup, the IM 912 defaults the MUX to pass all data and control linesdirectly from the master VPU to the output of the IM 912. As soon as theIM 912 sees one of the input TMDS I2C clocks toggling, it sets the MUXto pass that specific channel to the output. This includes the clock andall control signals, whether it is from the master or slave VPU. Thisallows the IM 912 to connect the default video card of the systemdirectly through to the monitor during power-up BIOS operation, evenbefore the drivers are aware of existence of the IM 912.

In the Dual VPU Interlink Mode, once the drivers are loaded, the driverscan detect if the IM 912 exists and if there are one or two connectionsto the IM 912. The detection is done by reading the I2C ID register ofthe IM 912 through the port of each VPU. The drivers can determine whichdiscovered connection is the master and which is the slave by the valueof bit 0 of the IM 912 ID register read on each port.

If only one connection is found, the IM 912 is left in Pass-throughmode. If two connections are found to the IM 912, the driver then takesover the screen control, setting the MUX of the IM 912 to output fromthe master port, with the VPU connected to the master port as the masterVPU. The clock is driven from this port until the power is lost or oneof the input connections to the IM 912 is broken.

The MUX of an embodiment is set by mechanisms that include Pass-Throughinitial states, AFR Manual Control, and Blacking Control. These modesand the particular controls for each are set through the TMDS CNTR bits,with the IM 912 responding on the next vertical blanking period. Themaster/slave switch (AFR_MAS) can latch in/occur on either the nextHSync or the next VSync depending on the I2C control bits setting.

In addition to using TDMS control registers, the drivers also controland monitor the IM functionality using I2C control registers.

I2C registers are used for control and monitoring that does not need tohappen every frame or faster. The registers can be available throughboth the master and slave ports of the IM.

For more dynamic control, the I2C control registers are used to setdifferent multiVPU modes and to manually switch the IM data path.

In one embodiment of a video processing system, inter-integrated circuitcommunication for the IM is accomplished using an Inter-IntegratedCircuit (I2C) bus. I2C is a bus typically used to connect integratedcircuits (ICs). I2C is a multi-master bus, which means that multiple ICscan be connected to the same bus and each one can act as a master byinitiating a data transfer.

FIG. 14 is diagram of an embodiment of an IM 912 on a dongle 1470,showing various I2C paths. The dongle 1470 receives data from a masterVPU A and a slave VPU B. In an embodiment, the master VPU A and theslave VPU B reside on one or more VPU card(s). In an embodiment, thereare three separate I2C buses for the IM 912. There is an I2C bus fromeach of two input ports, a master input port and a slave input port. Athird I2C bus goes from the IM 912 to a transmitter, and to anyconnected output device, such as panel and/or cathode ray tube (CRT).

The two input I2C buses each feed through the DVI master and slave inputports into the dongle 1470 and directly into the IM 912 on two separatechannels.

FIG. 15 is a diagram of I2C paths within the IM 912 according to anembodiment. The IM 912 includes a master identification (ID) I2Cregister and a slave ID I2C register. The IM 912 further includes an SDCtoggle sensor, a MUX, and other I2C registers.

Either of VPU A or VPU B can access the ID registers directly throughrespective input ports without concern for I2C bus ownership.

The IM 912 has one set of registers which are I2C accessible at aparticular I2C device address. All other addresses are passed throughthe IM 912 onto the I2C output port.

The master ID register and the slave register each have the sameinternal address, but are accessible only from their own respective I2Cbuses (slave or master).

Other than an IM_xxx_ID registers (offset 0) and the I2C_Reset register,the I2C bus is arbitrated on an I2C cycle-by-cycle basis, using afirst-come, first-served arbitration scheme.

For read cycles of the multi-byte registers, the ownership is held untilthe last byte is read. Software drivers insure that all bytes are fullyread in the bottom to top sequence. If all bytes are not fully read inthe bottom to top sequence, the bus may remain locked and the behaviormay become undefined.

For accesses that are passed through the IM 912 to external devices, theIM 912 does not understand page addressing or any cycle that requires adependency on any action in a prior access (cycles that extend for morethan one I2C stop bit). Therefore a register bit (CONTROL_BITS_2:Bit0:I2C_LOCK) is added. The software sets this register bit if a multi-I2Caccess is needed. When this register bit is set, the bus is given tothat port specifically until the bit is unset, at which time theautomatic arbitration resumes. In a case where both ports try to setthis bit, then the standard arbitration method determines which getsaccess, and a negative acknowledgement (NACK) signal is sent to let therequester know it was unsuccessful.

A specific I2C_Reset register is used in a case of the I2C bus becominglocked for some unexpected reason. Any read to this register, regardlessof I2C bus ownership, will always force the I2C state machines to resetand free up the I2C bus ownership, reverting back to the automaticarbitration.

For the other I2C registers, the I2C bus ownership is dynamicallyarbitrated for on a first-come, first-served fashion. The input portaccessing the other registers first with a clock and start bit getsownership for the duration of the current I2C cycle (that is, until thenext stop bit). For multiple-byte read registers (counters) on the IM912, the ownership is maintained from the first byte read until thefinal byte of the register has been read.

If an I2C access starts after the bus has been granted to another inputport, then a negative acknowledgement (NACK) signal is sent in responseto the access attempt. The data for a read is undefined and writes arediscarded.

The IM 912 supports single non-page type I2C accesses for accesses offof the IM 912. To allow for locking the I2C bus during multipledependent type I2C cycles, if an input port sets an I2C_LOCK bit(I2C_CONTROL_2:bit 0) to 1, the I2C bus is held in that port's ownershipuntil the same port sets the same bit back to 0. This register followsthe same first-come, first-served arbitration protocol.

If the I2C_RESET register is read from either port (no arbitration orownership is required), then the I2C state machine is reset and any I2Cownerships are cleared.

FIG. 16 is a diagram of I2C bus paths for a configuration in which amaster VPU A and an IM 912 are on the same VPU card 1652 according to anembodiment.

The VPU card 1652 could be part of the system 300 (FIG. 3), for example.The VPU card 1652 includes a master VPU 1608, an IM 912, a DVItransmitter and optional DVI transmitter. There are three I2C buses(master, slave, and interlink), as shown entering and existing the IM912. In one embodiment, the interlink I2C bus is a continuation of themaster I2C bus or slave I2C bus, depending on which bus is firstaccessed.

All IM 912 I2C registers are available to either the slave or master I2Cports. Standard NACK responses are used if the I2C bus is currently inuse by the other path. An IM 912 device ID is an exception and can beaccessed by either port at the same time.

In order to optionally verify that an I2C cycle has completedsuccessfully, all write registers are readable back. Since the I2Cregisters on the IM 912 do not time out, this matches the current methodof I2C accesses used on various conventional video cards. The read backshould not be necessary to verify writes.

The IM 912 I2C resets its state machine (not shown) every time it gets astop bit. This occurs at the start and end of every I2C cycle, accordingto known I2C protocol.

A CONTROL_ONESHOTS register (not shown) has a different behavior fromthe other read/write registers. Once written to, the IM 912 latches itsresults to internal control bits. The CONTROL_ONESHOTS registersthemselves are cleared on the next read of this register (allowing forconfirmation of the write).

The internal copies of the CONTROL_ONESHOTS bits are automaticallycleared by the IM 912 once the IM 912 has completed the requestedfunction and the CONTROL_ONESHOTS register corresponding bits arecleared. The IM 912 does not re-latch the internal versions until theI2C versions are manually cleared.

The IM has one set of registers which are I2C accessible. TheIM_MASTER_ID and IM_SLAVE_ID registers have the same internal addressbut are accessible only from their own I2C bus (e.g., slave or master).

The rest of the registers are only accessible from one side (master orslave) at a time.

In order to verify that an I2C cycle has completed successfully, allwrite registers must also be readable back to verify the updated values.Since the I2C registers on the IM do not time out, this is consistentwith conventional methods of I2C accesses used on various existing videocards. If needed, the read back should not be necessary to verify thewrites.

The IM I2C also resets its state machine every time it gets a stop bit.This happens as per I2C protocol at the start and end of every I2Ccycle.

The CONTROL_ONESHOTS register has a different behavior from the otherread/write registers. Once written to, the IM latches its results tointernal control bits. The CONTROL_ONESHOTS are cleared on the next readof this register (allowing for confirmation of the write).

The internal copies of the CONTROL_ONESHOTS bits are automaticallycleared by the IM once the IM has completed the requested function andthe CONTROL_ONESHOTS register corresponding bits are cleared.

In a dongle configuration, such as in systems 700 and 800, for example,the TMDS control bits are transmitted through the TMDS interface intothe IM. The software (driver) sets the registers within the VPU for thedesired control bit values and the results arrive at the TMDS receiverson the dongle and are latched into the IM. The AFR_MAN_ON* and AFR_AUTO*are latched on the rising edge of the TMDS VSync. No pixel data is beingtransmitted at this time. AFR_MAS is latched in on the rising edge ofeither HSync or VSync, depending on the setting in the I2C Control_Bitsregister, bit 5.

If the interlink_mode is not enabled (I2C register set), then the bitswill be ignored until it is enabled and will take place on the nextVSync.

If the interlink_mode is enabled, then the affect occurs on the verynext pixel data coming out of the IMs after the VSync or HSync as isappropriate.

If in pass-thru modes, the Syncs used are from the active path. If inAFR_MANual or blacking interlink modes, then the Syncs used are alwaysfrom the master path.

Aspects of the invention described above may be implemented asfunctionality programmed into any of a variety of circuitry, includingbut not limited to programmable logic devices (PLDs), such as fieldprogrammable gate arrays (FPGAs), programmable array logic (PAL)devices, electrically programmable logic and memory devices and standardcell-based devices, as well as application specific integrated circuits(ASICs) and fully custom integrated circuits. Some other possibilitiesfor implementing aspects of the invention include: microcontrollers withmemory (such as electronically erasable programmable read only memory(EEPROM)), embedded microprocessors, firmware, software, etc.Furthermore, aspects of the invention may be embodied in microprocessorshaving software-based circuit emulation, discrete logic (sequential andcombinatorial), custom devices, fuzzy (neural) logic, quantum devices,and hybrids of any of the above device types. Of course the underlyingdevice technologies may be provided in a variety of component types,e.g., metal-oxide semiconductor field-effect transistor (MOSFET)technologies like complementary metal-oxide semiconductor (CMOS),bipolar technologies like emitter-coupled logic (ECL), polymertechnologies (e.g., silicon-conjugated polymer and metal-conjugatedpolymer-metal structures), mixed analog and digital, etc.

Unless the context clearly requires otherwise, throughout thedescription and the claims, the words “comprise,” “comprising,” and thelike are to be construed in an inclusive sense as opposed to anexclusive or exhaustive sense; that is to say, in a sense of “including,but not limited to.” Words using the singular or plural number alsoinclude the plural or singular number respectively. Additionally, thewords “herein,” “hereunder,” “above,” “below,” and words of similarimport, when used in this application, refer to this application as awhole and not to any particular portions of this application. When theword “or” is used in reference to a list of two or more items, that wordcovers all of the following interpretations of the word: any of theitems in the list, all of the items in the list and any combination ofthe items in the list.

The above description of illustrated embodiments of the invention is notintended to be exhaustive or to limit the invention to the precise formdisclosed. While specific embodiments of and examples for, the inventionare described herein for illustrative purposes, various equivalentmodifications are possible within the scope of the invention, as thoseskilled in the relevant art will recognize. The teachings of theinvention provided herein can be applied to other systems, not only forthe system including graphics processing or video processing asdescribed above.

For example, a video image produced as described herein may be output toa variety of display devices, including computer displays that displaymoving pictures and printers that print static images.

The various operations described may be performed in a very wide varietyof architectures and distributed differently than described. As anexample, in a distributed system a server may perform some or all of therendering process. In addition, though many configurations are describedherein, none are intended to be limiting or exclusive. For example, theinvention can also be embodied in a system that includes an integratedgraphics processor (IGP) or video processor and a discrete graphics orvideo processor that cooperate to produce a frame to be displayed. Invarious embodiments, frame data processed by each of the integrated anddiscrete processors is merged or composited as described. Further, theinvention can also be embodied in a system that includes the combinationof one or more IGP devices with one or more discrete graphics or videoprocessors.

In other embodiments not shown, the number of VPUs can be more than two.

In other embodiments, some or all of the hardware and softwarecapability described herein may exist in a printer, a camera,television, handheld device, mobile telephone or some other device. Thevideo processing techniques described herein may be applied as part of aprocess of constructing animation from a video sequence.

The elements and acts of the various embodiments described above can becombined to provide further embodiments. These and other changes can bemade to the invention in light of the above detailed description.

All of the U.S. patent applications cited herein are hereby incorporatedby reference in their entirety.

In general, in the following claims, the terms used should not beconstrued to limit the video processing method and system to thespecific embodiments disclosed in the specification and the claims, butshould be construed to include any processing systems that operate underthe claims to provide video processing. Accordingly, the videoprocessing method and system is not limited by the disclosure, butinstead the scope of the video processing method and system is to bedetermined entirely by the claims.

While certain aspects of the method and apparatus for video processingare presented below in certain claim forms, the inventors contemplatethe various aspects of the method and apparatus for video processing inany number of claim forms. For example, while only one aspect of themethod and apparatus for video processing may be recited as embodied incomputer-readable medium, other aspects may likewise be embodied incomputer-readable medium. Accordingly, the inventors reserve the rightto add additional claims after filing the application to pursue suchadditional claim forms for other aspects of the method and apparatus forvideo processing.

What is claimed is:
 1. A device comprising: a plurality of processorsthat each couple to receive commands and data that correspond to framesof video that each comprise a plurality of pixels; and an interlinkmodule coupled to receive processed data corresponding to each framefrom each of the processors, the interlink module dividing a first frameinto a plurality of frame portions by dividing pixels of the first frameusing at least one balance point, the interlink module dynamicallydetermining a position for the balance point that minimizes a differencebetween a workload of any of the processors during processing ofcommands and data of at least one subsequent frame, the interlink modulefurther configurable to perform mixing of frame data, wherein a first ofthe plurality of processors operates in pass-through mode on a conditionthat the interlink module disables ones of the plurality of processors,wherein each of said plurality of processors render a divided portion ofa first frame using the at least one balance point and wherein theinterlink module dynamically adjusts the balance point in the firstframe using rendering information of a second frame, wherein the secondframe precedes the first frame, wherein a driver provides the commandsand data to the plurality of processors via a plurality of ring buffers,the ring buffers including at least a first ring buffer for the first ofthe plurality of processors.
 2. The device of claim 1, wherein theinterlink module determines a last processor of the plurality ofprocessors to complete rendering of a respective frame portion of thefirst frame.
 3. The device of claim 2, wherein the last processor writesan identifier to at least one memory location.
 4. The device of claim 3,wherein determining the last processor comprises reading the identifierfrom the memory location following the rendering.
 5. The device of claim2, wherein the interlink module dynamically adjusts the balance point toreduce a number of pixels processed by the last processor.
 6. The deviceof claim 5, wherein the interlink module renders a second frame usingthe dynamically adjusted balance point.
 7. The device of claim 1,wherein the dividing comprises horizontal dividing.
 8. The device ofclaim 1, wherein the dividing comprises vertical dividing.
 9. The deviceof claim 1, wherein the interlink module dynamically and incrementallyadjusts the balance point using at least one of display height, displaywidth, number of lines, and number of pixels.
 10. The device of claim 1,further comprising: determining that a second processor is rendering asmaller portion of the first frame than a first processor; and swappingdisplay regions rendered by the first processor and the secondprocessor.
 11. A device comprising: a plurality of processors that arecoupled to receive commands and data that correspond to frames of videothat each comprise a plurality of pixels; and an interlink modulecoupled to receive processed data corresponding to each frame from eachof the processors, the interlink module dividing a first frame into aplurality of frame portions by dividing pixels of the first frame usingat least one balance point, the interlink module determining a lastprocessor of the processors to complete rendering of a respective frameportion of the first frame using the balance point, the interlink moduledynamically adjusting the balance point to reduce a number of pixelsprocessed by the last processor and controlling rendering of a secondframe using the dynamically adjusted balance point of the frame thatsucceeds the first frame, the interlink module further configurable toperform mixing of frame data, wherein a first of the plurality ofprocessors operates in pass-through mode on a condition that theinterlink module disables ones of the plurality of processors, wherein adriver provides the commands and data to the plurality of processors viaa plurality of ring buffers, the ring buffers including at least a firstring buffer for the first of the plurality of processors.